Skip to content

Deploy->master - #76

Merged
susrisha merged 18 commits into
masterfrom
deploy-to-master
Jul 8, 2026
Merged

Deploy->master#76
susrisha merged 18 commits into
masterfrom
deploy-to-master

Conversation

@jeffmaki

@jeffmaki jeffmaki commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

Merge of deploy branch changes to master

@coderabbitai

coderabbitai Bot commented Jul 8, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@jeffmaki, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 16 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 0acf410e-52fb-4bde-9520-499cd53622b9

📥 Commits

Reviewing files that changed from the base of the PR and between 345b939 and f62c7a9.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (30)
  • components/AppImageViewer.vue
  • components/review/AttributeDiff.vue
  • components/review/Details.vue
  • components/review/FeatureImage.vue
  • components/review/FilterDropdown.vue
  • components/review/Item.vue
  • components/review/Map.vue
  • components/review/Overlay.vue
  • components/review/Sidebar.vue
  • components/review/Toolbar.vue
  • components/settings/panel/General.vue
  • nuxt.config.ts
  • package.json
  • pages/workspace/[id]/export/tdei.vue
  • pages/workspace/[id]/review.vue
  • plugins/v-viewer.client.ts
  • scripts/ci.sh
  • scripts/fix-lint.sh
  • services/changesets.ts
  • services/export/tdei.ts
  • services/index.ts
  • services/osm.ts
  • services/review.ts
  • services/tdei.ts
  • services/workspaces.ts
  • test/e2e/create-blank.spec.ts
  • test/e2e/create-file.spec.ts
  • types/tdei.ts
  • types/workspaces.ts
  • util/kartaview.ts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@jeffmaki jeffmaki changed the title Deploy to master Deploy->master Jul 8, 2026
jeffmaki and others added 5 commits July 7, 2026 21:58
The lockfile was regenerated on macOS, which resolved the oxc wasm
bindings' @emnapi optional deps to versions the Linux CI runner's
npm ci rejected (Missing @emnapi/core@1.11.2 / @emnapi/runtime@1.11.2).
Regenerated under the CI toolchain (node 24 / npm 11.16.0 on linux)
and verified npm ci passes; retains both linux and darwin bindings.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Nuxt 4 depends on vue-router@^5.1.0 and generates a tsconfig that
references the vue-router/volar/sfc-route-blocks Volar plugin, which
only exists in vue-router 5.x. The project pinned ^4.2.5, so a phantom
top-level vue-router@4.6.4 (no ./volar export) shadowed Nuxt's nested
5.1.0 and broke `nuxt typecheck` with ERR_PACKAGE_PATH_NOT_EXPORTED.
The app already runs on v5 at runtime via Nuxt. Verified npm ci +
nuxt typecheck pass on the CI toolchain (node 24 / npm 11.16.0, linux).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The "Improve mobile usability" refactor (7447e92) placed </span> and
#{{ id }} adjacent and moved the gap to a me-1 margin, which silently
dropped the space from the item's accessible name ("Feedback:#555"
instead of "Feedback: #555"), failing the review.spec ARIA snapshot.
Restore a real space between the type label and id (the space now
provides the visual gap, so me-1 is removed). Verified the e2e test
passes.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@jeffmaki
jeffmaki requested review from MashB and sureshgaussian July 8, 2026 02:45
@susrisha
susrisha merged commit db7244a into master Jul 8, 2026
2 checks passed
@susrisha
susrisha deleted the deploy-to-master branch July 8, 2026 09:25
@jeffmaki
jeffmaki restored the deploy-to-master branch July 8, 2026 23:37
@jeffmaki
jeffmaki deleted the deploy-to-master branch July 8, 2026 23:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants